fix(harness): wrap plugin hooks.json events under a top-level "hooks" key - #56
Merged
Merged
Conversation
… key
Claude Code's plugin hooks.json schema requires the event map (PostToolUse,
Stop, etc.) nested under a top-level "hooks" key -- same shape as the hooks
field inside settings.json. Ours had PostToolUse/Stop directly at the root,
which fails plugin load for every consumer with:
Failed to load hooks from .../hooks/hooks.json: [{"expected":"record",
"code":"invalid_type","path":["hooks"],"message":"Invalid input: expected
record, received undefined"}]
Caught while enabling the plugin in reDeploy.
robercano
approved these changes
Jul 6, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Claude Code's plugin
hooks/hooks.jsonschema requires the event map (PostToolUse,Stop, etc.) nested under a top-level"hooks"key — same shape as thehooksfield insidesettings.json. Ours hadPostToolUse/Stopdirectly at the root, which fails plugin load for every consumer:Caught while enabling the plugin in reDeploy (first real external consumer of the plugin install path).
Fix
Wrap the existing event map in
{"hooks": {...}}. No behavioral change to the hooks themselves — same matchers, same commands.Test plan
["hooks"]GATES_FILE=.claude/self/gates.json gate.sh lintpassesGATES_FILE=.claude/self/gates.json gate.sh testpasses